AI-Powered Discourse Content Analyzer: Accessibility Analysis Case Study
iSchoolConnect's Discourse Content Analyzer is a powerful AI tool that helps users rewrite their admissions essays and SOPs by providing structural and content-specific improvement tips.
However, product usage was at an all-time low despite reports of users telling their mentors they wish to use the tool.
A quantitative assessment of users' journeys was conducted to understand the blockers that prevented them from accessing the tool.
Product usage statistics alone revealed that there is a significant gap between the number of registered users and those who find their way to the tool.
Product usage statistics alone revealed that there is a significant gap between the number of registered users and those who find their way to the tool.
Furthermore, data revealed that amongst the users who used the tool, the most number of documents were uploaded by the in-house editor herself, thereby further lowering the number of actual student users.
A deeper analysis of the operations revealed significant roadblocks that prevented and demotivated users from engaging with the tool independently. This meant that users would often opt out of using the 'hard-to-find' tool and instead use Google Docs to get their SOP and essays reviewed by the editor. This action was also motivated by the fact that Google Docs allowed users and the editor to communicate changes via 'comments' and 'suggested edits'.
Recommendations:
- Adding a tool-specific button directly on the student's dashboard that allows them easy access to the tool.
- Adding a tool-specific button directly on the student's dashboard that allows them easy access to the tool.
- Simplifying the operational process further by allowing editors to drop comments as suggested changes within the tool, to prevent users from moving to google docs for their content reviews.
The operational changes improved product usage significantly. This also helped reduce the manual workload editors faced when users bypassed the tool and instead opted to use google docs for rewriting.
